Release 10.1A: OpenEdge Getting Started:
Progress OpenEdge Studio

Naming conventions

The AppBuilder creates structured procedure files, called window files, that are identified by a .w extension. For example, the source filename of the Customer SDB is bcust.w. It has a .r extension in its compiled form (bcust.r) and a prefix of h_ (for handle) when referred to as an instance in memory (h_bcust).

Other files commonly used with the AppBuilder are: include files (.i extension), procedure files (.p extension), and client proxy files (a _cl suffix added to the filename).

Table 4–1 lists the AppBuilder filename conventions.

Table 4–1: AppBuilder filename conventions

If a filename begins with...	Then the file is a...
b	SmartDataBrowser (SDB)
d	SmartDataObject (SDO)
g	SmartDialog
p	SmartPanel
sbo	SmartBusinessObject (SBO)
smr	Smart[Message]Receiver
sms	Smart[Message]Sender
sbb	SmartB2BObject
sdf	SmartDataField (SDF)
v	SmartDataViewer (SDV)
w	SmartWindow